Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0955

reference
322-tree-1
name
0955
tree-preservation-order

undefined

322-tpo-1
uprn
address-text
point
POINT (-1.018659 50.866574)
geometry
MULTIPOLYGON (((-1.018616 50.866570,-1.018618 50.866578,-1.018624 50.866585,-1.018633 50.866592,-1.018658 50.866597,-1.018671 50.866596,-1.018683 50.866592,-1.018693 50.866586,-1.018699 50.866579,-1.018701 50.866570,-1.018699 50.866562,-1.018693 50.866554,-1.018684 50.866548,-1.018672 50.866544,-1.018659 50.866543,-1.018646 50.866544,-1.018634 50.866548,-1.018625 50.866554,-1.018618 50.866561,-1.018616 50.866570)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL